9/29

# 4 Using the Oracle Big Data Appliance Configuration Utility

This chapter describes how to use the Oracle Big Data Appliance Configuration Utility. It contains the following sections:

- Overview of the Oracle Big Data Appliance Configuration Utility

- Using the Oracle Big Data Appliance Configuration Utility

- Network Configuration

- Software Configuration

Note:

The network administrator must check the network configuration, using the output files from the configuration utility, before the installation of Oracle Big Data Appliance. Otherwise, network errors may cause extensive delays. See "Preparing the Network for Oracle Big Data Appliance."

## 4.1 Overview of the Oracle Big Data Appliance Configuration Utility

The Oracle Big Data Appliance Configuration Utility is used to generate the installation and deployment files.

The utility is implemented as a spreadsheet containing these worksheets:

- Welcome

- Network Configuration

- Server Group Configuration (1 to 3 worksheets)

- Preview

An Oracle representative typically completes the Oracle Big Data Appliance Configuration Utility from information provided by the customer in the Oracle Big Data Appliance Configuration Worksheets. The customer and the Oracle representative work together to ensure that Oracle Big Data Appliance is configured correctly. For the sequence of steps involved in the configuration, see the Oracle Big Data Appliance Configuration Worksheets.

## 4.2 Using the Oracle Big Data Appliance Configuration Utility

This section explains how to use the Oracle Big Data Appliance Configuration Utility. It contains these topics:

- Using OpenOffice Spreadsheet

- Generating the Configuration Files

- About the Configuration Files

### 4.2.1 Using OpenOffice Spreadsheet

You must use Apache OpenOffice Spreadsheet 3.4 or Oracle Open Office Calc 3.3 to configure the spreadsheet. Do not use other spreadsheet programs like Microsoft Office Excel, which can modify the spreadsheet but not generate the files.

To obtain the Oracle Big Data Appliance Configuration Utility, refer to My Oracle Support Information Center ID 1445745.2.

To open the Oracle Big Data Appliance Configuration Utility:

1. Download OpenOffice from this website and follow the instructions for installing it:

   `http://www.openoffice.org/`

2. Open Apache OpenOffice Spreadsheet.

3. From OpenOffice Spreadsheet, open the bda_configurator.ods file. If the current settings do not allow macros, you see a message.

4. To change the macro setting:

   1. From the Tools menu, choose Options.

   2. In the navigation tree, expand the OpenOffice.org folder and select Security.

   3. In the right pane, click Macro Security.

   4. Either lower the security level or enter a trusted source.

5. To turn off AutoCorrect:

   1. From the Tools menu, choose AutoCorrect Options.

   2. Select the Options tab.

   3. Clear all check boxes, and then click OK.

   AutoCorrect settings can make it difficult for you to enter passwords.

6. Save your changes and reload the spreadsheet.

7. If you see a security warning, select Enable Macros.

### 4.2.2 Generating the Configuration Files

This procedure describes how to use the Oracle Big Data Appliance Configuration Utility to customize the default configuration settings for your installation. The other sections in this chapter provide detailed information about each field in the spreadsheet.

To generate the configuration files:

1. Open the spreadsheet with OpenOffice as described in the previous procedure.

2. On the Welcome page, choose the type of installation, then the layout of the servers from the drop-down menus. The layout choices vary depending on your choice of installation type.

3. Click Next to edit the Network Configuration sheet.

4. Enter the network configuration settings as specified in the Oracle Big Data Appliance Configuration Worksheets. If the server IP addresses are nonsequential, then you can enter them on the Preview page.

5. Click Next. If your changes are invalid, then you see an error message. You must correct the errors before continuing to the Server Group 1 sheet.

   To discard your changes, click Reset.

6. Enter the software configuration settings as specified in the Oracle Big Data Appliance Configuration Worksheets. If the group of servers is being added to an existing cluster, then all settings disappear from view.

7. Depending on your choices on the Welcome sheet, you must complete 1 to 3 Server Group sheets. Click Next to see the next Server Group sheet.

8. Click Preview to view the configuration settings defined by your entries. To make any changes, either click Previous, click the tab for a particular sheet, or enter the changes manually on the Preview page. You must click Preview on the Software Configuration sheet for any generated changes to appear on the Preview sheet.

9. When you are satisfied with the configuration, click Save Configuration on the Preview sheet to generate the configuration files.

   This step does not save the worksheet. To save your changes, click the Save icon.

10. Choose a location for the configuration files in the Select Path dialog box. The files are created in a directory named bda-customer_name/rack_name in that location, such as bda-Example Inc/bda1.

11. If you are configuring a single rack or part of a rack, then you are done. For a multirack cluster, complete the Network Configuration in a separate set of worksheets for each extension that is outside the primary rack.

12. Send the Installation Template to the network administrator to verify that the configuration is correct.

13. Send the final Installation Template, the hosts file, and the preinstall-checkip.sh script to the network administrator to prepare the network for the installation of Oracle Big Data Appliance.

### 4.2.3 About the Configuration Files

The Oracle Big Data Appliance Configuration Utility generates the following files to use when you configure the system. They are stored in a directory named bda-customer_name/rack_name, such as bda-Example Inc/bda1. If you configure multiple clusters for the rack, then the utility generates a directory for each one.

BdaDeploy.json

  Contains the network configuration for a full rack, a starter rack, or a starter rack with one in-rack expansion kit. It contains information about all the servers, switches, and PDUs. Transfer this file to a USB drive for copying to Oracle Big Data Appliance. See "Configuring the Network".

BdaExpansion.json

  Contains the network configuration for one or two in-rack expansion kits. It contains information about all the servers, but no information about the switches and PDUs. Transfer this file to a USB drive for copying to Oracle Big Data Appliance. See "Configuring the Network".

mammoth-rack_name.params

  Contains all information for a server group provided in the spreadsheet, including the network configuration, port numbers, default user names, and passwords. The spreadsheet creates a separate parameter file for each cluster. If several clusters are being configured, then each parameter file is located in a separate subdirectory named config/cluster_name. Transfer the files to a USB drive for copying to Oracle Big Data Appliance. See "Installing the Software on a New Rack".

  If an in-rack expansion kit is being configured as an addition to an existing cluster, then the spreadsheet does not generate a parameter file. The Mammoth utility generates it.

rack_name-bda-install-template.pdf

  Reproduces the Installation Preview page of the spreadsheet in a printable format. The network administrator and others can use this Installation Template to verify the settings and make any last minute corrections.

rack_name-hosts

  Lists the IP addresses and domains for all hosts on all networks:

  - Servers on the public (client) network

  - Servers on the administrative network

  - Servers on the private (InfiniBand) network

  - Oracle ILOMs on the administrative network

  - Switches and PDUs on the administrative network

rack_name-preinstall-checkip.sh

  Runs a series of tests to ensure the specified names and IP addresses for Oracle Big Data Appliance were added correctly to the name server, and they do not conflict with the existing network configuration. See "Preparing the Network for Oracle Big Data Appliance" for instructions on running this script.

  Figure 4-1 shows part of the first page of the Installation Template.

Figure 4-1 Installation Template

Description of "Figure 4-1 Installation Template"

## 4.3 Welcome Page

You must identify the type of equipment being delivered to the customer site and the planned configuration. Table 4-1 describes these options.

Table 4-1 General Properties for the Installation

Spreadsheet Field | Description
--- | ---
Type of Install | Lists various configurations, including a full rack, a starter rack, and one or two in-rack expansion kits. Your selection in this field restricts the list in Layout of Servers to applicable choices only.
Layout of Servers | Lists the available options for configuring groups of servers into CDH clusters. The number of groups controls the number of Server Group pages in the spreadsheet: one, two, or three.

## 4.4 Network Configuration

Table 4-2 to Table 4-6 briefly describe the fields in the Network Configuration sheet of the Oracle Big Data Appliance Configuration Utility. See the Oracle Big Data Appliance Configuration Worksheets for complete details.

Table 4-2 describes the general rack properties.

Table 4-2 General Properties for the Rack

Spreadsheet Field | Description
--- | ---
Rack Name | The name of the Oracle Big Data Appliance rack.
Server Base Name | Base name for all servers. A two-digit suffix uniquely identifies each server. The rack name and server base name are used to generate the host names for all network interfaces: eth0, bondib0, bondeth0, and Oracle ILOM. For example, a cluster name of `bda` and a server base name of `node` results in host names of bda1node01, bda1node02, and so forth.
Admin Access Suffix | Suffix to the basic host name to form the bondeth0 host names
Private Name Suffix | Suffix to the basic host name to form the bondib0 host name
ILOM Name Suffix | Suffix to the basic host name to form the Oracle ILOM name
Switch Base Name | Suffix to the rack name to form the base name for all switches. For example, a rack name of `bda` and a switch base name of `sw` results in switch names of bda02sw-ip, bda02sw-ib1, and so forth.
Customer Name | Name of the enterprise. Required.
Region | Region in which the Oracle Big Data Appliance is located. Click the field, and then click the arrow for a list of regions.
Time Zone | Time zone for your installation. You must select a region before selecting the time zone. Click the field, and then click the arrow for a list of time zones for the region.
Domain Name | Name of the domain in which Oracle Big Data Appliance operates. Required.
Will this rack be connected via InfiniBand to other racks? | Choose Yes or No.

Table 4-3 describes the network properties for the entire rack. If the site has isolated client and administrative networks with different DNS servers, NTP servers, or search domains, then complete this section for the client network and Table 4-7 for the administrative network.

Table 4-3 Network Properties for the Rack

Spreadsheet Field | Description
--- | ---
DNS Servers | Up to four IP addresses for the Domain Name System (DNS) servers. At least one DNS server must be accessible on the client network. DNS servers are not required on the administrative network, although Oracle Big Data Appliance uses them if they are available.
NTP Servers | Up to four IP addresses for the Network Time Protocol (NTP) servers. Both the client network and the administrative network must have access to at least one NTP server. The NTP server for the administrative network can be different from the NTP server for the client network.
Search Domains | Up to four domain names in which Oracle Big Data Appliance operates, such as `example.com` and `us.example.com`

Table 4-4 describes the network properties for individual servers in the rack. You specify the IP addresses assigned to node01. Sequential numbers are assigned automatically to the other servers. Ensure that an adequate range of addresses is free for each type of access. If sequential IP addresses are not available for the servers, then you can edit the Preview page.

Table 4-4 Network Properties for Servers

Spreadsheet Field | Description
--- | ---
Administrative - eth0 | First IP address of 18 from the administrative network
Private - bondib0 | First IP address of 18
Client Access - bondeth0 | First IP address of 18 from the client access network
ILOM | First IP address of 18 from the administrative network

Table 4-5 describes the network properties for all switches. You configure the switches manually, as described in Chapter 7. If three sequential IP addresses are not available for the InfiniBand switches, then you can edit the Preview page.

Table 4-5 Network Properties for Switches

Spreadsheet Field | Description
--- | ---
KVM Switch IP | IP address of the KVM switch. Not applicable to Oracle Big Data Appliance X3-2, which does not have a KVM switch.
Cisco Switch IP | IP address of the Cisco switch
First InfiniBand Switch IP | First IP address of three for the InfiniBand switches

Table 4-6 describes the network properties for the power distribution units (PDUs). You configure the PDUs manually, as described in Chapter 7.

Table 4-6 Network Properties for Power Distribution Units

Spreadsheet Field | Description
--- | ---
PDU A | IP address of the first power distribution unit
PDU B | IP address of the second power distribution unit

Table 4-7 describes the network properties for the administrative network if they are different from the client network. Typically, these properties are the same for both networks, and you can leave these fields blank. They default to the values you entered for the general network properties. See Table 4-3.

Table 4-7 Advanced Network Configuration Properties

Spreadsheet Field | Description
--- | ---
Admin Domain | The administrative domain name, if it is different from the domain you identified in the general rack properties.
Are administrative host name entries in the DNS? | Choose Yes or No.
Admin DNS Servers | Up to four IP addresses for the administrative Domain Name System server, if the addresses are different from those you provided for the general network properties.
Admin NTP Servers | Up to four IP addresses for the administrative Network Time Protocol server, if the addresses are different from those you provided for the general network properties.
Admin Search Domains | Up to four domain names in which Oracle Big Data Appliance administrative network operates, if the domains are different from those you provided for the general network properties.

## 4.5 Software Configuration

You can configure a group of servers as a CDH cluster, an Oracle NoSQL Database cluster, or an add-in to an existing cluster. You also have the option of leaving a group of servers unconfigured. Your selection of a cluster type affects the other software choices shown in the spreadsheet:

- CDH cluster: Fields for configuring Oracle NoSQL Database database are removed from view.

- Oracle NoSQL Database: Fields for configuring Oracle Big Data Connectors,MySQL Database, and Cloudera Manager are removed from view.

- Add-on to an existing cluster or not configured: All other fields are removed from view; there are no software configuration choices.

Table 4-8 to Table 4-12 briefly describe all fields in the Software Configuration sheet of the Oracle Big Data Appliance Configuration Utility.

Table 4-8 describes the optional software available for Oracle Big Data Appliance. If you have a license for Oracle Big Data Connectors, then you can install the software For more information about these components, see the Oracle Big Data Appliance Software User's Guide.

Table 4-8 Installed Components

Spreadsheet Field | Description
--- | ---
This group of servers is | You can create a new CDH (Hadoop) cluster, an Oracle NoSQL Database cluster, or add more servers to an existing cluster. If you are adding more servers to an existing cluster or not configuring the servers at this time, then you are done with the software configuration.
Cluster name | The name of the cluster is required information.
Are Big Data Connectors licensed? | Oracle Big Data Connectors facilitate data access between data stored in the CDH cluster and Oracle Database. The connectors require a separate license. If you have a license, choose Yes.
Install Oracle Data Integrator Agent? | The agent is a required component of Oracle Data Integrator, which is a graphical tool for performing extraction, transformation, and loading (ETL) of data into Oracle Database. To configure Oracle Data Integrator for use immediately, choose Yes.
Oracle NoSQL Database Edition? | For Oracle NoSQL Database clusters, choose Community Edition or, if you have a license, Enterprise Edition.

Table 4-9 describes the options for Auto Service Request (ASR). This service monitors the health of Oracle Big Data Appliance hardware. ASR Manager automatically submits a service request to Oracle Support Services when it detects a fault. See Chapter 5 for more information about ASR.

Table 4-9 Oracle Auto Service Request

Spreadsheet Field | Description
--- | ---
Enable Auto Service Request? | Although you can opt out of this service, Oracle strongly recommends that you enable ASR by choosing Yes.
ASR Manager Host | The fully qualified name of a Linux server on the network, where ASR will be installed
ASR Manager Port | The port number for ASR Manager. The default port is 162.
ASR Server Root Password | Password for `root` on the ASR Manager host

Table 4-10 identifies the users, groups, and passwords that can be set during the software installation. If you leave the passwords blank, then the installation prompts for them. The Oracle IDs must match those of a connected Oracle Exadata Database Machine to support the network file system (NFS) protocol.

Table 4-10 Users, Groups, and Passwords

Spreadsheet Field | Description
--- | ---
Cloudera Manager admin password | The password for the `admin` user for Cloudera Manager
root operating system password | The `root` password on all servers in the cluster.
oracle operating system password | The `oracle` password on all servers in the cluster. Oracle applications run under this identity.
oracle user ID | The ID number of the `oracle` user. It must match the `oracle` user ID of a connected Oracle Exadata Database Machine.
oinstall group ID | The ID number of the Oracle Inventory Group (`oinstall`). It must match the `oinstall` group ID of a connected Oracle Exadata Database Machine.
dba group ID | The ID number of the `dba` group. It must match the `dba` group ID of a connected Oracle Exadata Database Machine.
MySQL administration password | The password for the MySQL Database administrative user
MySQL password for Oracle Data Integrator | The password for the Oracle Data Integrator user in MySQL Database

Table 4-11 describes the configuration settings for the email server that Cloudera Manager uses to send alerts from the CDH cluster.

Table 4-11 Cloudera Manager Email Alerts

Spreadsheet Field | Description
--- | ---
Email Server (SMTP) Host | The fully qualified name of the existing SMTP server that the company uses on its internal network
Email Server (SMTP) Port | The port number used by the email server
Email Server uses authentication? | Choose Yes or No.
Email Server (SMTP) User Name | User name for Cloudera Manager to use for authentication on the SMTP server. This field is hidden when authentication is set to No.
Email Server (SMTP) Password | Password for the user name. This field is hidden when authentication is set to No.
Email Server uses SSL? | Choose Yes or No.
Email Alert Recipients | Up to four email addresses. These users receive the alerts from Cloudera Manager.

Table 4-12 describes the configuration settings for the Oracle Enterprise Manager system monitoring plugin for Oracle Big Data Appliance.

Table 4-12 Oracle Enterprise Manager Cloud Control

Spreadsheet Field | Description
--- | ---
Enable Enterprise Manager? | To use the Oracle Enterprise Manager system monitoring plugin, choose Yes.
Cloud Control host | The fully qualified name of the server where Oracle Enterprise Manager is installed with the plugin for Oracle Big Data Appliance.
Cloud Control user name | A Cloud Control user with super-administrative privileges to perform administrative `emcli` commands. Typically, this user is `sysman`.
Cloud Control password | Password for the Cloud Control user name.
Cloud Control registration password | The Enterprise Manager agent registration password for validating the Oracle Management agents on Oracle Big Data Appliance.
Cloud Control DBA SYS password | The `SYS` password for the Cloud Control repository.
OMS port | The port number for the Oracle Enterprise Manager Cloud Control web interface.
OMS upload port | The HTTP upload port number for Oracle Enterprise Manager Cloud Control web interface.